Apparatus, systems, and methods for single-sided locks

ABSTRACT

The disclosed apparatus may include a pin that is pushed in between two spokes of a wheel to lock the vehicle and removed from between the spokes of the wheel to unlock the vehicle. In one embodiment, a single-sided lock may include a pin holster for securing the pin while the vehicle is unlocked. In some embodiments, a single-sided lock mechanism may be permanently affixed to and/or built in to a vehicle, increasing the ease of use of the single-sided lock by preventing users from misplacing the lock. In one embodiment, a single-sided lock may include a mechanism for preventing accidental re-locking of a lock that has just been unlocked, further improving the user experience. Various other methods, systems, and apparatuses are also disclosed.

BACKGROUND

Some transportation services may provide transportation on demand,drawing from a transportation resource pool that includes vehicles ofmultiple types to meet the needs of those requesting transportation asthe needs arise. Including personal mobility vehicles such as bicyclesand scooters in a dynamic transportation network may enabletransportation requestors to complete portions of a journey moreefficiently. However, unlocking a personal mobility vehicle as the startof a journey and/or locking the personal mobility vehicles at the end ofthe journey may be points of friction that delay trips or increase userfrustration.

Many traditional systems for locking personal mobility vehicles may havedrawbacks, especially when used in the context of a dynamictransportation network. For example, a traditional cable lock may enablea user to lock a personal mobility vehicle associated with the dynamictransportation network to an additional vehicle, preventing others withlegitimate access to the additional vehicle from using the additionalvehicle. Some types of traditional locks may be clunky and, whenunlocked, interfere with the operation of the personal mobility vehicle.Some types of traditional locks may be unintuitive to users who have notpreviously operated a lock of that type, adding frustration and delay.Accordingly, the instant disclosure identifies and addresses a need foradditional and improved systems and methods for locks for wheeledvehicles.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodimentsand are a part of the specification. Together with the followingdescription, these drawings demonstrate and explain various principlesof the instant disclosure.

FIG. 1 is an illustration of a personal mobility vehicle secured inplace via a single-sided lock.

FIG. 2 is an illustration of a single-sided lock mounted on a personalmobility vehicle.

FIG. 3A is a side view of a PMV equipped with a single-sided lock in alocked state.

FIG. 3B is a rear view of a PMV equipped with a single-sided lock in alocked state.

FIG. 4 is an illustration of a pin component of a single-sided lock.

FIGS. 5A and 5B are illustrations of a wheel that is inhibited fromrotating via the pin of a single-sided lock.

FIG. 6A is a side view of a PMV equipped with a single-sided lock in anunlocked state.

FIG. 6B is a rear view of a PMV equipped with a single-sided lock in anunlocked state.

FIG. 7A is an isometric of a mount component of a single-sided lock.

FIG. 7B is a top view of a mount component of a single-sided lock.

FIG. 8 is an exploded view of a mount component of a single-sided lock.

FIG. 9 is a side view of a mount component of a single-sided lock.

FIGS. 10A, 10B, 10C, and 10D are illustrations of multiple cutaway viewsof a pin inserted into a single-sided lock.

FIGS. 11A, 11B, and 11C are illustrations of cutaway views of the actionof a cam at different positions during the operation of a single-sidedlock.

FIG. 12 is an illustration of a slider ring component of a single-sidedlock.

FIG. 13 is an exploded view of a cable component of a single-sided lock.

FIG. 14 is an illustration of a mount assembly for a single-sided lock.

FIG. 15 is a block diagram of an example system for a dynamictransportation network.

FIG. 16 is a flow diagram of an example method for assembling asingle-sided lock.

FIG. 17 is an illustration of an example requestor/provider managementenvironment.

FIG. 18 is an illustration of an example data collection and applicationmanagement system.

Throughout the drawings, identical reference characters and descriptionsindicate similar, but not necessarily identical, elements. While theexemplary embodiments described herein are susceptible to variousmodifications and alternative forms, specific embodiments have beenshown by way of example in the drawings and will be described in detailherein. However, the exemplary embodiments described herein are notintended to be limited to the particular forms disclosed. Rather, theinstant disclosure covers all modifications, equivalents, andalternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The present disclosure is generally directed to a single-sided lock forsecuring wheeled objects in place. Wheeled objects may include wheeledvehicles as well as non-vehicle objects such as carts, wheelbarrows, andsimilar. In some embodiments, a single-sided lock is may be lessphysically clunky than a U-lock or cable lock and/or may be morecompatible with small-wheeled vehicles such as scooters. For example, asingle-sided lock may be smaller and/or have a smaller insertablecomponent than other locks, rendering the single-sided lock morecompatible with small-wheeled vehicles. In some embodiments, asingle-sided lock may include a pin that is pushed in between two spokesof a wheel to lock the vehicle and removed from between the spokes ofthe wheel to unlock the vehicle. In one embodiment, a single-sided lockmay include a pin holster for securing the pin while the vehicle isunlocked (e.g., while the vehicle is in motion). In some embodiments, asingle-sided lock mechanism may be permanently affixed to and/or builtin to a vehicle, increasing the ease of use of the single-sided lock bypreventing users from misplacing the lock. In some examples, multiplesingle-sided locks may be affixed to a wheeled vehicle. For example, twosingle-sided locks may be affixed on opposite sides of a wheel. In oneembodiment, a single-sided lock may include a mechanism for preventingaccidental re-locking of a lock that has just been unlocked, furtherimproving the user experience.

Additionally, because locking and unlocking vehicles is a large part ofthe user experience when accessing transportation via personal mobilityvehicles (PMVs) such as scooters and bicycles, affixing the lock to thePMV may improve the user experience and the security of the PMV byeliminating the possibility that the user will misplace the lock. Insome embodiments, a rotating locking cable and anchor may securelyfasten a lock and/or a component of a lock (such as a pin) to a PMVwithout impeding a user's ability to lock and unlock the lock. In someembodiments, a rotating locking cable may rotate along multiple axes inorder to facilitate easy mobility of a pin between a lock and a pinholster. In one embodiment, a rotating locking cable may be constructedof sturdy components and/or may be at least a certain diameter toimprove the security of the lock.

As will be explained in greater detail below, a PMV equipped with asingle-sided lock may be part of a dynamic transportation matchingsystem may arrange transportation on an on-demand and/or ad-hoc basisby, e.g., matching one or more transportation requestors and/ortransportation requestor devices with one or more transportationproviders and/or transportation provider devices. For example, a dynamictransportation matching system may match a transportation requestor to atransportation provider that operates within a dynamic transportationnetwork (e.g., that is managed by, coordinated by, and/or drawn from bythe dynamic transportation matching system to provide transportation totransportation requestors).

In some examples, available sources of transportation within a dynamictransportation network may include vehicles that are owned by an ownerand/or operator of the dynamic transportation matching system.Additionally or alternatively, sources of transportation within adynamic transportation network may include vehicles that are ownedoutside of the dynamic transportation network but that participatewithin the dynamic transportation network by agreement. In someexamples, the dynamic transportation network may include lane-boundvehicles (e.g., cars, light trucks, etc.) that are designed,dimensioned, adapted, and/or required to operate within road lanes.Furthermore, the dynamic transportation network may include PMVs thatare capable of traversing routes not accessible to lane-bound vehicles,such as walking paths, sidewalks, and/or bicycle lanes. Additionally oralternatively, PMVs may operate with more agility and/or flexibilitythan lane-bound vehicles by, e.g., operating between road lanes (e.g.,lane splitting, operating abreast with other PMVs in the same road lane,etc.). Examples of PMVs may include, without limitation, manualbicycles, electrical bicycles, manual scooters, electrical scooters,and/or unicycles.

FIG. 1 illustrates a PMV secured in place via a single-sided lock. Insome examples, a single-sided lock may secure a wheeled vehicle to astationary object such as a docking station, bicycle rack, railing,and/or other stationary architectural feature. For example, a lock 104may secure a PMV 102 to a pillar 106. In some examples, a lock mayprevent a PMV or other wheeled vehicle from moving easily (e.g., bypreventing one of the wheels from rotating via the insertion of a pin)without securing the vehicle to another object. In some examples,securing PMV 102 to an object such as pillar 106 may be a secondarymeasure that further increases the difficulty of moving PMV 102, inaddition to the difficulty in moving PMV 102 caused by inhibiting themovement of the wheel. In some embodiments, lock 104 may be positionedon PMV 102 to facilitate locking PMV 102 to objects. In some examples,inhibiting the movement of a wheeled vehicle when the vehicle is not inuse may deter theft of the vehicle.

FIG. 2 illustrates a single-sided lock mounted on a PMV 202. Asillustrated in FIG. 2, in some embodiments, a single-sided lock mayinclude a cable 212 that originates from a cable mount 216 and connectsto a pin 204 that may be inserted into either an insertion point 206(e.g., to lock PMV 202) or a holster 210 (e.g., while unlocked) on amount 208. In some examples, pin 204 may generally represent any type ofinsertable lock component that is capable of being inserted between twoor more spokes of a wheel. In some embodiments, mount 208 may be affixedto PMV 202 such that insertion point 206 is adjacent to a wheel 214,enabling pin 204 to be inserted between two or more spokes of wheel 214.Although illustrated with a bicycle, a single-sided lock as illustratedin FIG. 2 may be similarly attached to a scooter or other type ofwheeled vehicle. In some embodiments, the single-sided lock may be builtin to a fender and/or other part of PMV 202. In some embodiments, asingle-sided lock may include multiple pins, such as two pins that areeach inserted between separate spokes of a wheel.

FIGS. 3A and 3B illustrate a single-sided lock in a locked state. Asillustrated in FIGS. 3A and 3B, PMV 202 may be equipped with a mount 208that includes insertion point 206 and/or holster 210. In some examples,pin 204 may be inserted into insertion point 206 that is positioned insuch a way that pin 204 is between spokes of wheel 214, inhibiting wheel214 from rotating and thus inhibiting PMV 202 from moving. In someembodiments, pin 204 may be coupled to PMV 202 via a flexible cable 212.In one embodiment, PMV 202 may be equipped with a display 302 thatdisplays a current status of the PMV based at least in part on a currentstatus of the lock. For example, display 302 may display an “unlocked”icon when pin 204 is not secured in place in insertion point 206 and/ora “locked” icon when pin 204 is secured in place in insertion point 206.Additionally or alternatively, display 302 may display a status of thePMV relative to a dynamic transportation network, such as “reserved”when it is allocated to a transportation requestor and/or “available”when it is not allocated to a transportation requestor.

In some embodiments, mount 208 and/or cable mount 216 may be positionedto facilitate locking PMV 202 to objects via cable 212. Additionally oralternatively, cable 212 may be dimensioned (e.g., in terms of length)and/or constructed (e.g., in terms of flexibility) to facilitate lockingPMV 202 to objects via wrapping cable 212 around an object and insertingpin 204 into insertion point 206. In one embodiment, cable mount 216 maybe affixed to a rear wheel cover 304 of PMV 202. In some embodiments,cable mount 216 may be affixed near a rear fork 306 and/or seat post 308of PMV 202. For example, cable mount 216 may be affixed to the top ofrear wheel cover 304 of PMV 202 just behind seat post 308 and rear fork306. In one embodiment, mount 208 may be affixed to and/or part of wheelcover 304. In some embodiments, mount 208 may be affixed to wheel cover304 just behind rear fork 306. In some embodiments, mount 208 may beaffixed to the side of wheel cover 304 towards the bottom of wheel cover304 (e.g., closer to the bottom edge of wheel cover 304 than the topedge of wheel cover 304). Mount 208 being positioned towards the bottomof wheel cover 304 while cable mount 216 is affixed to the top of wheelcover 304 may afford sufficient distance between mount 208 and cablemount 216 to facilitate looping and/or bending cable 212 around anobject (such as pillar 106 in FIG. 1) while pin 204 is locked intoinsertion point 216, effectively locking PMV 202 to the object. Inembodiments where both mount 208 and cable mount 216 are affixed towheel cover 304 near rear fork 306, the relative positions of mount 208and cable mount 216 may facilitate a diagonal positioning of cable 212when pin 204 is inserted into insertion point 216, enabling a user toposition cable 212 around a horizontal, vertical, or diagonal objectwith relative ease. For example, a user may position cable 212 around ahorizontal handrail, a vertical light post, and/or a diagonal stairwayrailing.

FIG. 4 illustrates pin 204 in detail. As illustrated in FIG. 4, pin 402may have a bevel 406 leading to an undercut 408. In some examples, bevel406 may push a slider out of the way as pin 402 enters the insertionpoint of a mount and the slider may then engage with undercut 408 tolock pin 402 in place within the mount and prevent pin 402 from beingremoved from the mount. In one embodiment, undercut 408 may be definedby a concavity in between bevel 406 and molding 416. In someembodiments, bevel 406 may not be present and pin 402 may havesubstantially parallel sides leading up to undercut 408. In oneembodiment, pin 204 may have a front bevel 404 that pushes a sliderand/or other components of a lock out of the way as pin 204 enters aninsertion point of the lock. In some embodiments, front bevel 404 maylead to a shaft 414 with substantially parallel sides. In oneembodiment, shaft 414 may contain a magnet 402 (not shown) that sensorson a lock mount may detect in order to determine the current locationand/or position of pin 204. In some embodiments, magnet 402 may extendthrough and/or past undercut 408. In one embodiment, pin 204 may have ahandle 410 that is contoured to be easily grasped by a user. In someembodiments, handle 410 may be substantially wider than shaft 414. Inone embodiment, handle 410 may have a flared base and/or rounded top.For example, handle base 418 may be large than the opening of insertionpoint 206, preventing pin 204 from being inserted into mount 208 pastmolding 416. In some embodiments, pin 204 may have a cable insertionpoint 412 at the top of handle 410. In one embodiment, cable 212 mayconnect to pin 204 via cable insertion point 412. In some embodiments,cable insertion point 412 may enable cable 212 to rotate relative to pin204.

FIGS. 5A and 5 B illustrate a wheel that is inhibited from rotating viathe pin of a single-sided lock. As illustrated in FIG. 5A, wheel 214 maybe free to rotate a small amount in rotation direction 502 before spoke504 encounters pin 204. However, in FIG. 5B, after wheel 214 has rotatedslightly in rotation direction 502, pin 204 inserted between two spokesof wheel 214 and held in place by mount 208 may inhibit further rotationof wheel 214 by preventing spoke 504 from passing pin 204 in due to thespokes being unable to rotate past pin 204, limiting the rotation ofwheel 214 to a very small angle and impeding the movement of a wheeledvehicle of which wheel 214 is a part. For example, when wheel 214 startsto rotate in rotation direction 502, spoke 504 may come into contactwith pin 204 and be unable to continue moving due to pin 204 beinglocked in place by mount 208, preventing wheel 214 from rotating anyfurther in rotation direction 502. In some embodiments, pin 204 may beheld in place by mount 208, not illustrated in FIG. 5. In someembodiments, pin 204 may, when inserted, go entirely through wheel 214and emerge from the other side. In other embodiments, pin 204, wheninserted, may reach far enough into wheel 214 to impede the movement ofspokes but may not reach all the way through wheel 214 and/or may notemerge from the other side of wheel 214. Although illustrated as abicycle wheel, in some embodiments, wheel 214 may represent a wheel ofanother type of wheeled vehicle, such as a scooter. Although a scooterwheel may have a smaller distance between the hub and the spokes and/orbetween individual spokes than a bicycle wheel, increasing thedifficulty of fitting a lock component in between spokes, pin 204 may bedimensioned to fit between the spokes of a scooter wheel.

FIGS. 6A and 6B illustrate a single-sided lock in an unlocked state. Insome examples, when pin 204 is not inserted into insertion point 206,pin 204 may be secured in holster 210 in mount 208. In one embodiment,holster 210 may form a hollow ring shape that is wide enough to permitthe shaft of pin 204 but not the handle of pin 204. Additionally oralternatively, holster 210 may be a solid enclosure that completelycovers pin 204 when pin 204 is inserted into holster 210. In oneembodiment, holster 210 may be equipped with a mechanism such as aclasp, lock, and/or magnet that secures pin 204 in place in holster 210.Additionally or alternatively, holster 210 may be angled such that pin204 is at least partially held in place in holster 210 by gravity and/ormay be dimensioned such that pin 204 is at least partially held in placein holster 210 by friction. In some embodiments, holster 210 may bepositioned and/or angled to reduce the chances of a holstered pininterfering with the mobility of a user of PMV 202 (e.g., by being inthe way of the user's leg and/or catching on the user's clothing). Inone embodiment, holster 210 may be angled such that pin 204, wheninserted into holster 210, is perpendicular to rear fork 306. In someembodiments, cable 212 may be just long enough for pin 204 to reachholster 210 (given the flexibility of cable 212), reducing the chancesthat cable 212 will become tangled and/or otherwise interfere with themotion of PMV 202. In one embodiment, holster 210 may be positioned suchthat, when pin 204 is inserted into holster 210, cable 212 may issuefrom cable mount 216 in a direction that is parallel or at an acuteangle to wheel 214, reducing the changes that cable 212 will becomecaught on an obstruction and unholster pin 204.

FIGS. 7A and 7B illustrate a mount component of a single-sided lock. Asillustrated in FIGS. 7A and 7B, a mount 208 may have an insertion pointthat includes a locking sleeve 708 and/or a spring 718. In someembodiments, locking sleeve 708 may, in combination with a slider 714,function as a locking mechanism to secure a pin 204 in place when pin204 is inserted. For example, locking sleeve 708 may have an openingthat permits the head of slider 714 to enter into the insertion pointand secure pin 204 in place. In one embodiment, slider 714 may bedimensioned to include a concavity that fits a cam (such as cam 716) andenables the cam to move the slider between extended and retractedpositions by rotating the cam to push the slider forwards and/orbackwards. Additionally or alternatively, slider 714 may be dimensionedwith a slider head that fits a concavity within a pin (such as undercut408 illustrated in FIG. 4), enabling slider 714 to prevent the pin frommoving forward or backward when the slider head is inserted into theconcavity within the pin. In some embodiments, a portion of slider 714may be dimensioned to interact with a spring that, when expanded, pushesslider 714 into the extended position. In one embodiment, slider 714 mayextend into insertion point 208 when extended (e.g., via an opening inlocking sleeve 708) and/or may not extend into insertion point 208 whenretracted. In some examples, spring 718 may compress when pin 204 isinserted and/or may propel pin 204 entirely or partially out of mount208 when slider 714 is retracted from the insertion point. In someembodiments, a spring 706 may be compressed when slider 714 is retractedand/or may push slider 714 into place to lock pin 204 in place. In oneembodiment, a switch 712 and/or a switch 713 may move in response to themotion of slider 714 and/or the motion of a motor 704 that moves and/orlocks slider 714 in position. In some embodiments, motor 704 may rotatea cam 716 that moves slider 714 between locked (extended) and unlocked(retracted) positions. In some examples, switch 712 and/or switch 713may, when depressed by one or more teeth of a gear 720 of motor 704,track and/or send information about the current position of slider 714to another component. In one embodiment, switch 712 and/or switch 713may include an electrical switch. Additionally or alternatively, thesystems described herein may track the position of pin 204 by using amagnetic field detector in mount 208 to detect the position of a magnetin pin 204. In some embodiments, mount 208 may include and/orcommunicate with a communication module that sends information about theposition of pin 204 and/or slider 714 to a server. For example, theserver may be part of a dynamic transportation matching system thatmanages a dynamic transportation network with which the wheeled vehiclesto which the single-sided lock is affixed is associated. In someembodiments, the server may update a status of the wheeled vehiclerelative to the dynamic transportation network (e.g., available,unavailable, and/or allocated) based at least in part on the position ofpin 204 (e.g., by setting the status to available if pin 204 is in thelocked position). In some examples, based on information about theposition and/or motion of pin 204 that indicates that pin 204 has justbeen removed from the insertion point, motor 704 may rotate cam 716 tolock slider 714 into the extended position, preventing pin 204 frombeing re-inserted and returning the lock to the locked state. In someembodiments, motor 704 may rotate cam 716 to enable slider 714 to returnto the retracted position after a set period of time after pin 204 hasbeen removed from the insertion point and/or may enable slider 714 toreturn to the retracted position after receiving a signal (e.g., from aserver and/or a lock and/or PMV component that communicates with aserver). Additionally or alternatively, motor 704 may rotate cam 716 toenable slider 714 to return to the retracted position after one or moresensors (e.g., a magnetic field sensor that detects a magnet within pin204) detects that pin 204 is no longer inserted into mount 208.

FIG. 8 is an exploded view of mount 208. As illustrated in FIG. 8,locking sleeve 708 may house a pin eject bushing 802 and/or springcarrier 804 that may work in conjunction with spring 718 to eject thepin from mount 208 by enabling spring 718 to, when expanded, eject thepin from mount 208. In some embodiments, slider 714 may be coupled to aslider gasket 806 that helps prevent liquid from entering mount 208 byforming a watertight seal with mount 208 as slider 714 moves betweenretracted and extended states. In one embodiment, switch 712 and switch713 may separately track the movement and/or position of motor 704and/or slider 714, respectively. For example, switch 712 may track theposition of motor 704 to determine at what position motor 704 must stopto be in each lock state. In one example, switch 713 may track theposition of slider 714. When slider 714 is in the retracted state,switch 713 may be open because motor 704 may, via cam 716, be pullingthe slider 714 into a housing for slider 714. When slider 714 is in theextended state, spring 706 may push slider 714 outward and into switch713, causing switch 713 to be closed when slider 714 is in the extendedstate.

FIG. 9 is a side view of mount 208 with pin 204 inserted. As illustratedin FIG. 9, with pin 204 inserted into mount 208, slider 714 may lockinto place in a groove within pin 204. With slider 714 extended, spring706 may also be extended. In some examples, switch 713 may changeposition based on the position of slider 714. In some embodiments, pin204 may include a beveled edge and/or undercut such that, when pin 204is inserted into mount 208, slider 714 is initially pushed out of theway by pin 204 into the retracted position, causing spring 706 to coil,and is then pushed into the extended position by spring 706 once pin 204is fully inserted such that the undercut of pin 204 lines up with slider714. Alternatively, pin 204 may have a beveled tip and/or may not have abevel before the undercut.

FIGS. 10A, 10B, 10C, and 10D illustrate a slider in four differentpositions. In FIG. 10A, at position 1002, slider 714 is fully extended.In some embodiments, slider 714 may be pushed into the extended positionby spring 706. Additionally or alternatively, motor 704 (not visible)may lock slider 714 into the extended position, preventing pin 208 frombeing inserted into insertion point 206 past bevel 406 (and thuspreventing the lock from locking). In one embodiment, spring 718 may bepartially compressed by pin 204 as pin 204 is partially inserted intoinsertion point 206.

In FIG. 10B, at position 1004, pin 204 may be inserted farther intoinsertion point 206 than in position 1002, such that bevel 406 contactsslider 714 and pushes slider 714 into a retracted position, compressingspring 706. In some embodiments, pin 204 may also further compressspring 718. In FIG. 10C, at position 1006, pin 204 may be fully insertedinto insertion point 206 such that bevel 406 has moved past the head ofslider 714. In one embodiment, spring 706 may expand, pushing the headof slider 714 into undercut 408 in pin 204. In some examples, motor 704may lock slider 714 into place, preventing pin 204 from being removedfrom insertion point 206 due to bevel 406 being unable to travel pastthe head of slider 714 (and therefore locking the lock). In someembodiments, pin 204 may fully compress spring 718 when pin 204 is fullyinserted into insertion point 206.

In FIG. 10D, at position 1010, motor 704 may move slider 714 into theretracted position, compressing spring 706 and removing slider 714 fromundercut 408 of pin 204. In one embodiment, spring 718 may expand,ejecting pin 204 from insertion point 206 (and unlocking the lock). Insome embodiments, motor 704 may then lock slider 714 into an extendedstate, preventing the immediate re-insertion of pin 204 into insertionpoint 206.

FIGS. 11A, 11B, and 11C illustrate the motion of a motor-driven cam atdifferent positions. In some embodiments, cam 716 may be oblong in shapeand/or may be rotated via the action of motor 704. In some embodiments,cam 716 may be adjacent to gear 720 of motor 704 that may have threeteeth at ninety-degree angles and one surface free of teeth and may berotated in conjunction with cam 716. In FIG. 11A, cam 716 may beoriented vertically along the long axis of cam 716 such that cam 716 isnot in contact with slider 714, enabling slider 714 to moveindependently of cam 716. In some examples, the action of a spring(e.g., spring 706 illustrated in FIG. 6) may push slider 714 into theextended position without cam 716 acting on slider 714 and/or preventingthe motion of slider 714. For example, if a pin is not currentlyinserted into insertion point 208, motor 704 rotate cam 716 so that cam716 does not have contact with slider 714, enabling slider 714 to bepushed from the extended position to the retracted position by theinsertion of a pin and/or to be pushed (e.g., via spring 706) from theretracted position to the extended position once a concavity of the pin(e.g., undercut 408 illustrated in FIG. 4) lines up with slider 714. Insome examples, motor 704 may then rotate cam 716 such that cam 716 isoriented horizontally and in contact with slider 714, locking slider 714into the extended position (thus locking the lock).

In FIG. 11B, cam 716 may have, via rotation into a horizontalorientation with the longest portion of cam 716 oriented towardsinsertion point 208, driven slider 714 into the extended position, wherepart of slider 714 extends into insertion point 206 of mount 208. Insome embodiments, motor 704 may lock cam 716 in place, causing cam 716to lock slider 714 into the extended position. If a pin has previouslybeen inserted into insertion point 208, slider 714 may lock the pin inplace (i.e., the single-sided lock may be locked). If no pin is insertedinto insertion point 206 and slider 714 is locked into the extendedposition by the rotation of cam 716 as driven by motor 704, slider 714may prevent the insertion of a pin and/or other objects into insertionpoint 206. In some examples, this configuration may prevent a user fromaccidentally re-locking the lock by re-inserting the pin after havingpreviously unlocked the lock and removed the pin. In some embodiments,motor 704 may rotate gear 720 while rotating cam 716, causing one ormore teeth of gear 720 to depress the plate of a switch (e.g., switch712 illustrated in FIG. 7B) that detects information about the rotationof cam 716. Additionally or alternatively, the motion of slider 714 mayopen or close switch 713 that detects the position of slider 714.

In FIG. 11C, cam 716 has, via rotating into a horizontal orientationsuch that the longest portion of cam 716 is oriented away from insertionpoint 206, driven slider 714 into the retracted position, where slider714 is not protruding into insertion point 206 of mount 208. In someexamples, motor 704 may lock cam 716 into this rotational position andtherefore lock slider 714 into the retracted position. In someembodiments, if a pin is currently inserted into insertion point 206,rotating cam 716 to move slider 714 into the retracted position mayenable the pin to be withdrawn from insertion point 208 (unlocking thelock).

FIG. 12 illustrates a slider ring component of a single-sided lock. Insome embodiments, slider 714 may be coupled to a gasket 706. In oneembodiment, gasket 706 may be a rubber o-ring. In some examples, gasket706 may move with slider 714, preventing liquid from entering the mountat the insertion point by forming a physical barrier where there mightotherwise exist a void that liquid could enter.

FIG. 13 is an exploded view of a cable assembly for a single-sided lock.As illustrated in FIG. 13, in some embodiments, a cable assembly for acable that attaches the pin of a single-sided lock to a vehicle mayinclude a vehicle-side termination 1314 anchored to the vehicle by avehicle bushing 1330 and/or capped by a mount lid 1310 and/or a mountcap top 1306 held in place by one or more screws 1308. In oneembodiment, vehicle-side termination 1314 may include two circularattachments joined at a substantially perpendicular angle, at least oneof which includes threading to enable attachment to components withmatching but reversed threading. In one embodiment, mount lid 1310and/or mount cap top 1306 may be circular with smooth sides, preventingthe cable assembly from catching on objects (e.g., the clothing of anoperator of a PMV to which the cable assembly is affixed) and/orimproving aesthetics. In some embodiments, vehicle-side termination 1314may also be coupled to a fitting 1312. In one embodiment, a cable 1304may be coupled to vehicle-side termination 1314 on one end and a pin1302 on the other end. In some embodiments, a pin handle cover 1318 maybe coupled to pin 1302 where pin 1302 meets cable 1304 and/or a pinhandle 1326. In some embodiments, vehicle-side termination 1314 mayrotate relative to the vehicle to which vehicle-side termination 1314 isaffixed around rotational axis 1320. For example, vehicle-sidetermination 1314 may rotate on a plane substantially perpendicular tothe surface of the vehicle to which vehicle-side termination 1314 isattached. In some embodiments, cable 1304 may rotate within and/orrelative to vehicle-side termination 1314 around rotational axis 1322.In one embodiment, rotational axis 1320 may be substantiallyperpendicular to rotational axis 1322. Additionally or alternatively,pin 1302 may rotate relative to cable 1304 and/or pin handle cover 1318around rotational axis 1324. In some embodiments, a crimped fitting 1328may facilitate the rotation of pin 1302 relative to cable 1304. Incombination with the flexibility of cable 1304, rotational axes 1320,1322, and/or 1324 may facilitate easy movement of pin 1302 into and outof an insertion point and/or holster. In some embodiments, duringassembly, cable 1304 may passes through pin handle 1326 and terminate atcrimped fitting 1328, sandwiching pin handle 1326 between cable 1304 andcrimped fitting 1328 but allowing for cable 1304 to rotate on rotationalaxis 1324. Pin handle 1326 may then be screwed onto pin 1302 and/orwelded in place, creating a permanent assembly between the pin handle1326 and pin 1302 so that pin 1302 is able to rotate freely while havinga permanent attachment to cable 1304.

FIG. 14 illustrates a mount assembly for a single-sided lock. In someembodiments, a mount assembly may include a bracket 1414 that securesthe mount assembly to the fender and/or rigid frame of a wheeled vehiclesuch as a bicycle. In some embodiments, bracket 1414 may include a thinsheet of metal, plastic, and/or other material that is shaped with twosubstantially perpendicular angles such that bracket 1414 fits directlyover the fender of a wheeled vehicle with minimal space between bracket1414 and the fender. In one embodiment, bracket 1414 may includemultiple attachment points such as screws that secure bracket 1414 tothe fender and/or other structural component of the wheeled vehicle. Inone embodiment, bracket 1414 may be coupled to a mount 1408 such that aninsertion point 1410 is positioned adjacent to a wheel. In someembodiments, mount 1408 may be integral to bracket 1414. In someembodiments, bracket 1414 may include a cable mount 1412 that is coupledto a cable 1402 that secures a pin 1404 to the mount assembly. In someembodiments, the mount assembly may include a holster 1406 that is notdirectly attached to bracket 1414 and/or that secures pin 1404 in placewhen pin 1404 is not inserted into insertion point 1410. In someembodiments, holster 1406 may be affixed to and/or integral to bracket1414. In some embodiments, cable 1402 may be dimensioned such that cable1402 is long enough to wrap around a bike rack, pole, tree, and/or otherstationary object and still insert pin 1404 into insertion point 1410.For example, cable 1402 may be one foot long, eighteen inches long, twofeet long, and/or three feet long. In some embodiments, pin 1404 may bedimensioned such that when pin 1404 is fully inserted into insertionpoint 1410, pin 1404 prevents full rotation a wheel. For example, pin1404 may be two inches long, three inches long, or four inches long. Insome embodiments, bracket 1414 may be dimensioned based at least in parton the dimensions of the vehicle to which bracket 1414 will be attached.For example, the height of bracket 1414 may be based on the diameter ofthe wheel of the vehicle and/or the way in which the wheel and/orbracket 1414 is mounted to the frame of the vehicle. In someembodiments, mount 1414 may be dimensioned to house all of thecomponents within mount 1414 (e.g., as illustrated in FIGS. 7 and 8).

FIG. 15 illustrates an example system 1500 for matching transportationrequests with a dynamic transportation network that includes personalmobility vehicles and/or other wheeled vehicles. As shown in FIG. 15, adynamic transportation matching system 1510 may be configured with oneor more dynamic transportation matching modules 1512 that may performone or more of the steps described herein. Dynamic transportationmatching system 1510 may represent any computing system and/or set ofcomputing systems capable of matching transportation requests. Dynamictransportation matching system 1510 may be in communication withcomputing devices in each of a group of vehicles 1520. Vehicles 1520 mayrepresent any vehicles that may fulfill transportation requests. In someexamples, vehicles 1520 may include disparate vehicle types and/ormodels. For example, vehicles 1520 may include road-going vehicles andpersonal mobility vehicles. In some examples, some of vehicles 1520 maybe standard commercially available vehicles. According to some examples,some of vehicles 1520 may be owned by separate individuals (e.g.,transportation providers). Furthermore, while, in some examples, many orall of vehicles 1520 may be human-operated, in some examples many ofvehicles 1520 may also be autonomous (or partly autonomous).Accordingly, throughout the instant disclosure, references to a“transportation provider” (or “provider”) may, where appropriate, referto an operator of a human driven vehicle, an autonomous vehicle controlsystem, an autonomous vehicle, an owner of an autonomous vehicle, anoperator of an autonomous vehicle, an attendant of an autonomousvehicle, a vehicle piloted by a requestor, and/or an autonomous systemfor piloting a vehicle. While FIG. 15 does not specify the number ofvehicles 1520, it may be readily appreciated that the systems describedherein are applicable to hundreds of vehicles, thousands of vehicles, ormore. In one example, dynamic transportation matching system 1510 maycoordinate transportation matchings within a single region for 50,000vehicles or more on a given day. In some examples, vehicles 1520 maycollectively form a dynamic transportation network that may providetransportation supply on an on-demand basis to transportationrequestors.

As mentioned above, dynamic transportation matching system 1510 maycommunicate with computing devices in each of vehicles 1520. Thecomputing devices may be any suitable type of computing device. In someexamples, one or more of the computing devices may be integrated intothe respective vehicles 1520. In some examples, one or more of thecomputing devices may be mobile devices. For example, one or more of thecomputing devices may be smartphones. Additionally or alternatively, oneor more of the computing devices may be tablet computers, personaldigital assistants, or any other type or form of mobile computingdevice. According to some examples, one or more of the computing devicesmay include wearable computing devices (e.g., a driver-wearablecomputing device), such as smart glasses, smart watches, etc. In someexamples, one or more of the computing devices may be devices suitablefor temporarily mounting in a vehicle (e.g., for use by a requestorand/or provider for a transportation matching application, a navigationapplication, and/or any other application suited for the use ofrequestors and/or providers). Additionally or alternatively, one or moreof the computing devices may be devices suitable for installing in avehicle and/or may be a vehicle's computer that has a transportationmanagement system application installed on the computer in order toprovide transportation services to transportation requestors and/orcommunicate with dynamic transportation matching system 1510.

As shown in FIG. 15, vehicles 1520 may include provider devices1530(1)-(n) (e.g., whether integrated into the vehicle, permanentlyaffixed to the vehicle, temporarily affixed to the vehicle, worn by adriver of the vehicle, etc.). In some examples, provider devices 1530may include a provider apps 1540(1)-(k). Provider apps 1540(1)-(k) mayrepresent any application, program, and/or module that may provide oneor more services related to operating a vehicle and/or providingtransportation matching services. For example, provider apps 1540(1)-(k)may include a transportation matching application for providers and/orone or more applications for matching PMVs with requestor devices. Insome embodiments, different types of provider vehicles may beprovisioned with different types of provider devices and/or differentprovider applications. For example, PMVs may be provisioned withprovider devices that are configured with a provider application thatenables transportation requestors to reserve and/or operate the PMVwhile road-constrained vehicles (e.g., cars) may be provisioned withprovider devices that are configured with a provider application thatenables provider vehicle operators (e.g., transportation providers) torespond to requests from transportation requestors. In some examples,provider applications 1540(1)-(k) may match the user of provider apps1540(1)-(k) (e.g., a transportation provider) with transportationrequestors through communication with dynamic transportation matchingsystem 1510. In addition, and as is described in greater detail below,provider apps 1540(1)-(k) may provide dynamic transportation managementsystem 1510 with information about a provider (including, e.g., thecurrent location of the provider and/or vehicle) to enable dynamictransportation management system 1510 to provide dynamic transportationmatching and/or management services for the provider and one or morerequestors. In some examples, provider apps 1540(1)-(k) may coordinatecommunications and/or a payment between a requestor and a provider.According to some embodiments, provider apps 1540(1)-(k) may provide amap service, a navigation service, a traffic notification service,and/or a geolocation service.

Additionally, as shown in FIG. 15, dynamic transportation matchingsystem 1510 may communicate with requestor devices 1550(1)-(m). In someexamples, requestor devices 1550 may include a requestor app 1560.Requestor app 1560 may represent any application, program, and/or modulethat may provide one or more services related to requestingtransportation matching services. For example, requestor app 1560 mayinclude a transportation matching application for requestors. In someexamples, requestor app 1560 may match the user of requestor app 1560(e.g., a transportation requestor) with transportation providers throughcommunication with dynamic transportation matching system 1510. Inaddition, and as is described in greater detail below, requestor app1560 may provide dynamic transportation management system 1510 withinformation about a requestor (including, e.g., the current location ofthe requestor) to enable dynamic transportation management system 1510to provide dynamic transportation matching services for the requestorand one or more providers. In some examples, requestor app 1560 maycoordinate communications and/or a payment between a requestor and aprovider. According to some embodiments, requestor app 1560 may providea map service, a navigation service, a traffic notification service,and/or a geolocation service.

Embodiments of the instant disclosure may include or be implemented inconjunction with a dynamic transportation matching system. Atransportation matching system may arrange transportation on anon-demand and/or ad-hoc basis by, e.g., matching one or moretransportation requestors with one or more transportation providers. Forexample, a transportation matching system may provide one or moretransportation matching services for a ridesharing service, aridesourcing service, a taxicab service, a car-booking service, anautonomous vehicle service, a personal mobility vehicle service, or somecombination and/or derivative thereof. The transportation matchingsystem may include and/or interface with any of a variety of subsystemsthat may implement, support, and/or improve a transportation matchingservice. For example, the transportation matching system may include amatching system (e.g., that matches requestors to ride opportunitiesand/or that arranges for requestors and/or providers to meet), a mappingsystem, a navigation system (e.g., to help a provider reach a requestor,to help a requestor reach a provider, and/or to help a provider reach adestination), a reputation system (e.g., to rate and/or gauge thetrustworthiness of a requestor and/or a provider), a payment system,and/or an autonomous or semi-autonomous driving system. Thetransportation matching system may be implemented on various platforms,including a requestor-owned mobile device, a computing system installedin a vehicle, a requestor-owned mobile device, a server computer system,or any other hardware platform capable of providing transportationmatching services to one or more requestors and/or providers.

FIG. 16 illustrates an example method 1600 for constructing asingle-sided lock. As illustrated in FIG. 16, at step 1610, one or moreof the systems described herein may couple a pin to a cable. At step1620, one or more of the systems described herein may couple the cableto a mount that includes an insertion point for the pin. At step 1630,one or more of the systems described herein may couple the mount to awheeled vehicle such that the insertion point for the pin is adjacentand substantially perpendicular to a wheel of the wheeled vehicle. Insome embodiments, one or more of the systems described herein maydetect, via a sensor within the mount (e.g., a switch), that the pin hasbeen inserted into the insertion point and/or send, to a server, amessage that the pin has been inserted into the insertion point.Additionally or alternatively, one or more of the systems describedherein may detect, via a sensor within the mount, that the pin has beenremoved from the insertion point and/or send, to a server, a messagethat the pin has been removed from the insertion point.

FIG. 17 shows a transportation management environment 1700, inaccordance with various embodiments. As shown in FIG. 17, atransportation management system 1702 may run one or more servicesand/or software applications, including identity management services1704, location services 1706, ride services 1708, and/or other services.Although FIG. 17 shows a certain number of services provided bytransportation management system 1702, more or fewer services may beprovided in various implementations. In addition, although FIG. 17 showsthese services as being provided by transportation management system1702, all or a portion of any of the services may be processed in adistributed fashion. For example, computations associated with a servicetask may be performed by a combination of transportation managementsystem 1702 (including any number of servers, databases, etc.), one ormore devices associated with a provider (e.g., devices integrated withmanaged vehicles 1714(a), 1714(b), and/or 1714(c); provider computingdevices 1716 and tablets 1720; and transportation management vehicledevices 1718), and/or more or more devices associated with a riderequestor (e.g., the requestor's computing devices 1724 and tablets1722). In some embodiments, transportation management system 1702 mayinclude one or more general purpose computers, server computers,clustered computing systems, cloud-based computing systems, and/or anyother computing systems or arrangements of computing systems.Transportation management system 1702 may be configured to run any orall of the services and/or software components described herein. In someembodiments, the transportation management system 1702 may include anappropriate operating system and/or various server applications, such asweb servers capable of handling hypertext transport protocol (HTTP)requests, file transfer protocol (FTP) servers, database servers, etc.

In some embodiments, identity management services 1704 may be configuredto perform authorization services for requestors and providers and/ormanage their interactions and/or data with transportation managementsystem 1702. This may include, e.g., authenticating the identity ofproviders and determining that they are authorized to provide servicesthrough transportation management system 1702. Similarly, requestors'identities may be authenticated to determine whether they are authorizedto receive the requested services through transportation managementsystem 1702. Identity management services 1704 may also manage and/orcontrol access to provider and/or requestor data maintained bytransportation management system 1702, such as driving and/or ridehistories, vehicle data, personal data, preferences, usage patterns as aride provider and/or as a ride requestor, profile pictures, linkedthird-party accounts (e.g., credentials for music and/or entertainmentservices, social-networking systems, calendar systems, task-managementsystems, etc.) and any other associated information. Transportationmanagement system 1702 may also manage and/or control access to providerand/or requestor data stored with and/or obtained from third-partysystems. For example, a requester or provider may grant transportationmanagement system 1702 access to a third-party email, calendar, or taskmanagement system (e.g., via the user's credentials). As anotherexample, a requestor or provider may grant, through a mobile device(e.g., 1716, 1720, 1722, or 1724), a transportation applicationassociated with transportation management system 1702 access to dataprovided by other applications installed on the mobile device. In someexamples, such data may be processed on the client and/or uploaded totransportation management system 1702 for processing.

In some embodiments, transportation management system 1702 may provideride services 1708, which may include ride matching and/or managementservices to connect a requestor to a provider. For example, afteridentity management services module 1704 has authenticated the identitya ride requestor, ride services module 1708 may attempt to match therequestor with one or more ride providers. In some embodiments, rideservices module 1708 may identify an appropriate provider using locationdata obtained from location services module 1706. Ride services module1708 may use the location data to identify providers who aregeographically close to the requestor (e.g., within a certain thresholddistance or travel time) and/or who are otherwise a good match with therequestor. Ride services module 1708 may implement matching algorithmsthat score providers based on, e.g., preferences of providers andrequestors; vehicle features, amenities, condition, and/or status;providers' preferred general travel direction and/or route, range oftravel, and/or availability; requestors' origination and destinationlocations, time constraints, and/or vehicle feature needs; and any otherpertinent information for matching requestors with providers. In someembodiments, ride services module 1708 may use rule-based algorithmsand/or machine-learning models for matching requestors and providers.

Transportation management system 1702 may communicatively connect tovarious devices through networks 1710 and/or 1712. Networks 1710 and1712 may include any combination of interconnected networks configuredto send and/or receive data communications using various communicationprotocols and transmission technologies. In some embodiments, networks1710 and/or 1712 may include local area networks (LANs), wide-areanetworks (WANs), and/or the Internet, and may support communicationprotocols such as transmission control protocol/Internet protocol(TCP/IP), Internet packet exchange (IPX), systems network architecture(SNA), and/or any other suitable network protocols. In some embodiments,data may be transmitted through networks 1710 and/or 1712 using a mobilenetwork (such as a mobile telephone network, cellular network, satellitenetwork, or other mobile network), a public switched telephone network(PSTN), wired communication protocols (e.g., Universal Serial Bus (USB),Controller Area Network (CAN)), and/or wireless communication protocols(e.g., wireless LAN (WLAN) technologies implementing the IEEE 902.12family of standards, Bluetooth, Bluetooth Low Energy, Near FieldCommunication (NFC), Z-Wave, and ZigBee). In various embodiments,networks 1710 and/or 1712 may include any combination of networksdescribed herein or any other type of network capable of facilitatingcommunication across networks 1710 and/or 1712.

In some embodiments, transportation management vehicle device 1718 mayinclude a provider communication device configured to communicate withusers, such as drivers, passengers, pedestrians, and/or other users. Insome embodiments, transportation management vehicle device 1718 maycommunicate directly with transportation management system 1702 orthrough another provider computing device, such as provider computingdevice 1716. In some embodiments, a requestor computing device (e.g.,device 1724) may communicate via a connection 1726 directly withtransportation management vehicle device 1718 via a communicationchannel and/or connection, such as a peer-to-peer connection, Bluetoothconnection, NFC connection, ad hoc wireless network, and/or any othercommunication channel or connection. Although FIG. 17 shows particulardevices communicating with transportation management system 1702 overnetworks 1710 and 1712, in various embodiments, transportationmanagement system 1702 may expose an interface, such as an applicationprogramming interface (API) or service provider interface (SPI) toenable various third parties which may serve as an intermediary betweenend users and transportation management system 1702.

In some embodiments, devices within a vehicle may be interconnected. Forexample, any combination of the following may be communicativelyconnected: vehicle 1714, provider computing device 1716, provider tablet1720, transportation management vehicle device 1718, requestor computingdevice 1724, requestor tablet 1722, and any other device (e.g., smartwatch, smart tags, etc.). For example, transportation management vehicledevice 1718 may be communicatively connected to provider computingdevice 1716 and/or requestor computing device 1724. Transportationmanagement vehicle device 1718 may establish communicative connections,such as connections 1726 and 1728, to those devices via any suitablecommunication technology, including, e.g., WLAN technologiesimplementing the IEEE 902.12 family of standards, Bluetooth, BluetoothLow Energy, NFC, Z-Wave, ZigBee, and any other suitable short-rangewireless communication technology.

In some embodiments, users may utilize and interface with one or moreservices provided by the transportation management system 1702 usingapplications executing on their respective computing devices (e.g.,1716, 1718, 1720, and/or a computing device integrated within vehicle1714), which may include mobile devices (e.g., an iPhone®, an iPad®,mobile telephone, tablet computer, a personal digital assistant (PDA)),laptops, wearable devices (e.g., smart watch, smart glasses, headmounted displays, etc.), thin client devices, gaming consoles, and anyother computing devices. In some embodiments, vehicle 1714 may include avehicle-integrated computing device, such as a vehicle navigationsystem, or other computing device integrated with the vehicle itself,such as the management system of an autonomous vehicle. The computingdevice may run on any suitable operating systems, such as Android®,iOS®, macOS®, Windows®, Linux®, UNIX®, or UNIX®-based or Linux®-basedoperating systems, or other operating systems. The computing device mayfurther be configured to send and receive data over the Internet, shortmessage service (SMS), email, and various other messaging applicationsand/or communication protocols. In some embodiments, one or moresoftware applications may be installed on the computing device of aprovider or requestor, including an application associated withtransportation management system 1702. The transportation applicationmay, for example, be distributed by an entity associated with thetransportation management system via any distribution channel, such asan online source from which applications may be downloaded. Additionalthird-party applications unassociated with the transportation managementsystem may also be installed on the computing device. In someembodiments, the transportation application may communicate or sharedata and resources with one or more of the installed third-partyapplications.

FIG. 18 shows a data collection and application management environment1800, in accordance with various embodiments. As shown in FIG. 18,management system 1802 may be configured to collect data from variousdata collection devices 1804 through a data collection interface 1806.As discussed above, management system 1802 may include one or morecomputers and/or servers or any combination thereof. Data collectiondevices 1804 may include, but are not limited to, user devices(including provider and requestor computing devices, such as thosediscussed above), provider communication devices, laptop or desktopcomputers, vehicle data (e.g., from sensors integrated into or otherwiseconnected to vehicles), ground-based or satellite-based sources (e.g.,location data, traffic data, weather data, etc.), or other sensor data(e.g., roadway embedded sensors, traffic sensors, etc.). Data collectioninterface 1806 can include, e.g., an extensible device frameworkconfigured to support interfaces for each data collection device. Invarious embodiments, data collection interface 1806 may be extended tosupport new data collection devices as they are released and/or toupdate existing interfaces to support changes to existing datacollection devices. In various embodiments, data collection devices maycommunicate with data collection interface 1806 over one or morenetworks. The networks may include any network or communication protocolas would be recognized by one of ordinary skill in the art, includingthose networks discussed above.

As shown in FIG. 18, data received from data collection devices 1804 canbe stored in data store 1808. Data store 1808 may include one or moredata stores, such as databases, object storage systems and services,cloud-based storage services, and other data stores. For example,various data stores may be implemented on a non-transitory storagemedium accessible to management system 1802, such as historical datastore 1810, ride data store 1812, and user data store 1814. Data stores1808 can be local to management system 1802, or remote and accessibleover a network, such as those networks discussed above or a storage-areanetwork or other networked storage system. In various embodiments,historical data 1810 may include historical traffic data, weather data,request data, road condition data, or any other data for a given regionor regions received from various data collection devices. Ride data 1812may include route data, request data, timing data, and other riderelated data, in aggregate and/or by requestor or provider. User data1814 may include user account data, preferences, location history, andother user-specific data. Although certain data stores are shown by wayof example, any data collected and/or stored according to the variousembodiments described herein may be stored in data stores 1808.

As shown in FIG. 18, an application interface 1816 can be provided bymanagement system 1802 to enable various apps 1818 to access data and/orservices available through management system 1802. Apps 1818 may run onvarious user devices (including provider and requestor computingdevices, such as those discussed above) and/or may include cloud-basedor other distributed apps configured to run across various devices(e.g., computers, servers, or combinations thereof). Apps 1818 mayinclude, e.g., aggregation and/or reporting apps which may utilize data1808 to provide various services (e.g., third-party ride request andmanagement apps). In various embodiments, application interface 1816 caninclude an API and/or SPI enabling third party development of apps 1818.In some embodiments, application interface 1816 may include a webinterface, enabling web-based access to data 1808 and/or servicesprovided by management system 1802. In various embodiments, apps 1818may run on devices configured to communicate with application interface1816 over one or more networks. The networks may include any network orcommunication protocol as would be recognized by one of ordinary skillin the art, including those networks discussed above, in accordance withan embodiment of the present disclosure.

While various embodiments of the present disclosure are described interms of a ridesharing service in which the ride providers are humandrivers operating their own vehicles, in other embodiments, thetechniques described herein may also be used in environments in whichride requests are fulfilled using autonomous vehicles. For example, atransportation management system of a ridesharing service may facilitatethe fulfillment of ride requests using both human drivers and autonomousvehicles.

As detailed above, the computing devices and systems described and/orillustrated herein broadly represent any type or form of computingdevice or system capable of executing computer-readable instructions,such as those contained within the modules described herein. In theirmost basic configuration, these computing device(s) may each include atleast one memory device and at least one physical processor.

In some examples, the term “memory device” generally refers to any typeor form of volatile or non-volatile storage device or medium capable ofstoring data and/or computer-readable instructions. In one example, amemory device may store, load, and/or maintain one or more of themodules described herein. Examples of memory devices include, withoutlimitation, Random Access Memory (RAM), Read Only Memory (ROM), flashmemory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical diskdrives, caches, variations or combinations of one or more of the same,or any other suitable storage memory.

In some examples, the term “physical processor” generally refers to anytype or form of hardware-implemented processing unit capable ofinterpreting and/or executing computer-readable instructions. In oneexample, a physical processor may access and/or modify one or moremodules stored in the above-described memory device. Examples ofphysical processors include, without limitation, microprocessors,microcontrollers, Central Processing Units (CPUs), Field-ProgrammableGate Arrays (FPGAs) that implement softcore processors,Application-Specific Integrated Circuits (ASICs), portions of one ormore of the same, variations or combinations of one or more of the same,or any other suitable physical processor.

Although illustrated as separate elements, the modules described and/orillustrated herein may represent portions of a single module orapplication. In addition, in certain embodiments one or more of thesemodules may represent one or more software applications or programsthat, when executed by a computing device, may cause the computingdevice to perform one or more tasks. For example, one or more of themodules described and/or illustrated herein may represent modules storedand configured to run on one or more of the computing devices or systemsdescribed and/or illustrated herein. One or more of these modules mayalso represent all or portions of one or more special-purpose computersconfigured to perform one or more tasks.

In addition, one or more of the modules described herein may transformdata, physical devices, and/or representations of physical devices fromone form to another. Additionally or alternatively, one or more of themodules recited herein may transform a processor, volatile memory,non-volatile memory, and/or any other portion of a physical computingdevice from one form to another by executing on the computing device,storing data on the computing device, and/or otherwise interacting withthe computing device.

In some embodiments, the term “computer-readable medium” generallyrefers to any form of device, carrier, or medium capable of storing orcarrying computer-readable instructions. Examples of computer-readablemedia include, without limitation, transmission-type media, such ascarrier waves, and non-transitory-type media, such as magnetic-storagemedia (e.g., hard disk drives, tape drives, and floppy disks),optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks(DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-statedrives and flash media), and other distribution systems.

The process parameters and sequence of the steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

The preceding description has been provided to enable others skilled inthe art to best utilize various aspects of the exemplary embodimentsdisclosed herein. This exemplary description is not intended to beexhaustive or to be limited to any precise form disclosed. Manymodifications and variations are possible without departing from thespirit and scope of the instant disclosure. The embodiments disclosedherein should be considered in all respects illustrative and notrestrictive. Reference should be made to the appended claims and theirequivalents in determining the scope of the instant disclosure.

Unless otherwise noted, the terms “connected to” and “coupled to” (andtheir derivatives), as used in the specification and claims, are to beconstrued as permitting both direct and indirect (i.e., via otherelements or components) connection. In addition, the terms “a” or “an,”as used in the specification and claims, are to be construed as meaning“at least one of.” Finally, for ease of use, the terms “including” and“having” (and their derivatives), as used in the specification andclaims, are interchangeable with and have the same meaning as the word“comprising.”

What is claimed is:
 1. An apparatus comprising: a pin that, wheninserted between spokes of a wheel of a wheeled vehicle, limits therotation of the wheel; and a mount for securing the pin to the wheeledvehicle that comprises: at least one insertion point for the pin thatsecures the pin in place; at least one attachment point that enables themount to be attached to the wheeled vehicle such that the at least oneinsertion point for the pin is positioned adjacent to the spokes of thewheel; a slider that is configured to extend into the at least oneinsertion point and engage with the pin to secure the pin within the atleast one insertion point; a rotatable cam that is configured to engagewith the slider at differing positions of the rotatable cam such that: afirst position of the rotatable cam permits the slider to moveindependently of the rotatable cam, permitting the pin to be insertedinto the at least one insertion point; a second position of therotatable cam causes the slider to retract from the at least oneinsertion point, enabling the pin to be removed from the at least oneinsertion point; and a third position of the rotatable cam secures theslider in a configuration that extends into the at least one insertionpoint, preventing the pin from being inserted into the at least oneinsertion point; and wherein the slider comprises a concavity disposedon one side of the slider and configured to receive the cam therein. 2.The apparatus of claim 1, further comprising a cable that connects thepin to at least one of the mount and the wheeled vehicle.
 3. Theapparatus of claim 1, further comprising a pin holster that is adaptedto secure the pin to the wheeled vehicle when the pin is not insertedbetween the spokes of the wheel.
 4. The apparatus of claim 3, whereinthe pin holster comprises a clasp configured to secure the pin withinthe pin holster.
 5. The apparatus of claim 1, wherein the mountcomprises a spring that compresses when the pin is inserted anddecompresses to expel the pin.
 6. The apparatus of claim 1, wherein thepin comprises a beveled edge that narrows towards an end of the pin thatis inserted between the spokes of the wheel.
 7. The apparatus of claim1, wherein the pin comprises a beveled edge that tapers away from anundercut such that, as the pin is inserted between the spokes of thewheel, the beveled edge pushes aside the slider housed in the mount thatthen engages with the undercut to lock the pin into position.
 8. Theapparatus of claim 7, further comprising a switch that tracks a currentposition of the slider to determine whether the pin is inserted.
 9. Theapparatus of claim 1, wherein the mount comprises an o-ring that movesas the pin is inserted into the at least one insertion point to preventliquid from entering the at least one insertion point.
 10. The apparatusof claim 1, wherein the first position of the rotatable cam permits theslider to be pushed from an extended position to a retracted position byinsertion of the pin into the at least one insertion point.
 11. A systemcomprising: a pin that, when inserted between spokes of a wheel of awheeled vehicle, limits the rotation of the wheel; and. a mount forsecuring the pin to the wheeled vehicle that comprises: at least oneinsertion point for the pin that secures the pin in place when the pinis inserted between the spokes of the wheel; at least one attachmentpoint that enables the mount to be attached to the wheeled vehicle suchthat the at least one insertion point for the pin is positioned adjacentto the spokes of the wheel; a slider that is configured to extend intothe at least one insertion point and engage with the pin to secure thepin within the at least one insertion point; a rotatable cam that isconfigured to engage with the slider at differing positions of therotatable cam such that: a first position of the rotatable cam permitsthe slider to move independently of the rotatable cam, permitting thepin to be inserted into the at least one insertion point; a secondposition of the rotatable cam causes the slider to retract from the atleast one insertion point, enabling the pin to be removed from the atleast one insertion point; and a third position of the rotatable camsecures the slider in a configuration that extends into the at least oneinsertion point, preventing the pin from being inserted into the atleast one insertion point; and wherein the slider comprises a concavitydisposed on one side of the slider and configured to receive the camtherein.
 12. The system of claim 11, further comprising at least onesensor that detects the position of the pin relative to the mount. 13.The system of claim 11, further comprising at least one electricalswitch that is configured to detect a position of the slider.
 14. Thesystem of claim 11, further comprising at least one electrical switchthat is configured to detect a position of the cam.
 15. The system ofclaim 11, further comprising a communication module that is configuredto send information about the position of the pin to a server.
 16. Thesystem of claim 11, further comprising a display surface that displays,based at least in part on the position of the pin, a status of thewheeled vehicle.
 17. The system of claim 11, wherein the wheeled vehiclecomprises a bicycle.
 18. A method comprising: coupling a pin to a cable;coupling the cable to a mount that comprises: an insertion point for thepin; an attachment point that enables the mount to be attached to awheeled vehicle; a slider that is configured to extend into theinsertion point and engage with the pin to secure the pin within theinsertion point; a rotatable cam that is configured to engage with tslider differing positions of the rotatable cam such that: a firstposition of the rotatable cam permits the slider to move independentlyof the rotatable cam, permitting the pin to be inserted into theinsertion point; a second position of the rotatable cam causes theslider to retract from the insertion point, enabling the pin to beremoved from the insertion point; and a third position of the rotatablecam secures the slider in a configuration that extends into theinsertion point, preventing the pin from being inserted into theinsertion point; and wherein the slider comprises a concavity disposedon one side of the slider and configured to receive the cam therein; andcoupling, by the attachment point, the mount to a wheeled vehicle suchthat the insertion point for the pin is adjacent and substantiallyperpendicular to a wheel of the wheeled vehicle.
 19. The method of claim18, further comprising: detecting, via a sensor within the mount, thatthe pin has been inserted into the insertion point; and sending, to aserver, a message that the pin has been inserted into the insertionpoint.
 20. The method of claim 18, further comprising detecting, via asensor within the mount, that the pin has been removed from theinsertion point; and sending, to a server, a message that the pin hasbeen removed from the insertion point.